PageProps Type Errors in Next.js

[Universe0809]

Select Topic Area

Bug

Body

Hello everyone,
I am working on a project using Next.js 15 and have defined my page as follows:
export default async function Page({ params }: { params: { slug: string[] } }) { ... }

However, during the build process, I encounter the following TypeScript error:
Type error: Type '{ params: { slug: string[]; }; }' does not satisfy the constraint 'PageProps'. Types of property 'params' are incompatible. Type '{ slug: string[]; }' is missing the following properties from type 'Promise<any>': then, catch, finally, [Symbol.toStringTag]

Could you advise on how to correctly resolve these type issues or effectively suppress this error? I've attempted to use the comment // @ts-expect-error: params type does not match expected PageProps, but the error persists.

Thank you for your assistance!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Aninooo]

error happens because TypeScript thinks params should be a Promise, not a plain object.
Use Type Assertion: Tell TypeScript to ignore the type issue by adding as any:

export default async function Page({ params }: { params: { slug: string[] } } as any) {
// ur function code here
}

[night-fury-3]

Hi @Universe0809,
It appears that there are breaking changes in Next.js version 15 related to properties such as params. The official documentation highlights this issue (see: Next.js v15 Upgrade Guide).

To address these changes, you have a couple of options:

1. Downgrade: Consider reverting to an earlier version of Next.js where these breaking changes do not apply.
2. Update your Code: You can handle the params by awaiting them in your function as follows:
   `type Params = Promise<{ slug: string[] }>;

export default async function Page({ params }: { params: Params }) {
const { slug } = await params;
}`

This approach ensures that your application remains compatible with the latest version of Next.js.

Thank you for taking my suggestion into account.
Please feel free to contact me if you have any questions.

[dev-eneandre]

It helped me also, thank you!

[sadsisadsj]

alienmaster806@gmail.com

[sadsisadsj]

I want that friend's gmail and password to be fixed for me

[dhanushd-27]

thanks bud!

I wish god blesses you with a good pc

[ayush-khatrii]

Thanks!

[mohsinparvi]

Here’s how I fix this issse:

import Link from "next/link";
import photos, { Photo } from "@/lib/";
import PhotoCard from "@/components/photo-card";
export const generateStaticParams = () => {
  return photos.map(({ id }) => ({
    id: String(id),
  }));
};
export type paramsType = Promise<{ id: string }>;

export default async function PhotoPage(props: { params: paramsType }) {
  const { id } = await props.params;
  const photo: Photo | undefined = photos.find((p) => p.id === id);

  if (!photo) {
    return <div>Photo not found</div>;
  }

  return (
    <section className="py-24">
      <div className="container">
        <div>
          <Link
            href="/photos"
            className="font-semibold italic text-sky-600 underline"
          >
            Back to photos
          </Link>
        </div>
        <div className="mt-10 w-1/3">
          <PhotoCard photo={photo} />
        </div>
      </div>
    </section>
  );
}

[suhailkhan123517]

thank you very very much bro

[theognd]

Thanks !!!

[soosho]

Here’s how I fix this issse:

import Link from "next/link";
import photos, { Photo } from "@/lib/";
import PhotoCard from "@/components/photo-card";
export const generateStaticParams = () => {
  return photos.map(({ id }) => ({
    id: String(id),
  }));
};
export type paramsType = Promise<{ id: string }>;

export default async function PhotoPage(props: { params: paramsType }) {
  const { id } = await props.params;
  const photo: Photo | undefined = photos.find((p) => p.id === id);

  if (!photo) {
    return <div>Photo not found</div>;
  }

  return (
    <section className="py-24">
      <div className="container">
        <div>
          <Link
            href="/photos"
            className="font-semibold italic text-sky-600 underline"
          >
            Back to photos
          </Link>
        </div>
        <div className="mt-10 w-1/3">
          <PhotoCard photo={photo} />
        </div>
      </div>
    </section>
  );
}

thank you, i love you

[byleonardlim]

2025 and this saved my frustrating times! Thank you!

[damien-schneider]

If you’ve encountered the same issue I did, it was due to having a monorepo with multiple React dependencies. Specifically, one of my packages was still using React 18, which caused a type mismatch.

[ThomasLaukkanen]

I had the same issue but it was more than one file that needed to be changed. So if anyone encounters the same issue just run this command in the terminal. It will fix all the files for you. npx @next/codemod@canary next-async-request-api .

[7kylor]

hans't solve the issue for me!

[kulterryan]

Is next turning into a too much opinionated framework?

[Debbl]

[mic-andrew]

Delete this!

[im-Kazmi]

if someone have a client page with hooks or some other client side stuff you can split the components in two with a server component passing params to the client component.

import { ClientPage } from "./client-page";

export type paramsType = Promise<{ id: string }>;

type Props = {
  params: paramsType;
};

const Page = async ({ params }: Props) => {
  const { id } = await params;
  return <ClientPage id={id} />;
};

export default Page;

"use client";

import { HeaderActions } from "./_components/header-actions";
import { EnvSelector } from "./_components/env-selector";
import { PromptEditor } from "./_components/prompt-editor";
import { SettingsPanel } from "./_components/settings-panel";
import { Playground } from "./_components/playground";

import { ShadowWrapper } from "@/app/(authenticated)/components/shadow-wrapper";
import { useGetCircut } from "@repo/features/circut";

type Props = {
  id: string;
};
export const ClientPage = ({ id }: Props) => {
  const { data, isLoading, isPending } = useGetCircut(id);

  return (
    <div className="flex min-h-screen">
      <ShadowWrapper>
        <div className="flex-1">
          <HeaderActions />
          <EnvSelector />
          <div className="container mx-auto max-w-7xl">
            <div className="grid grid-cols-3 gap-8 p-8">
              <div className="col-span-2">
                <PromptEditor />
                <Playground />
              </div>
              <div className="col-span-1">
                <SettingsPanel />
              </div>
            </div>
          </div>
        </div>
      </ShadowWrapper>
    </div>
  );
};

[Stan4394]

I was able to solve the issue with codemods: npx @next/codemod@latest next-async-request-api .

[Pyrex77]

Your a fuckin genius I love you

…

On Mon, Jan 27, 2025, 1:47 PM Stan4394 ***@***.***> wrote: I was able to solve the issue with codemods: npx @***@***.*** next-async-request-api . — Reply to this email directly, view it on GitHub <#142577 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNILBZAX3ER5P2K55AX7EQ32MZ5LHAVCNFSM6AAAAABQSZS72CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJXGM4DSNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[manisense]

I wont go when we use useState in the same file. we cant use useState along with async func.. should i consider removing all the useStates??

[GIThubuserms]

import React from 'react';

export type paramsType = Promise<{ id: string }>;

type Props = {
params: paramsType;
};

const Page = async ({ params }: Props) => {
const { id } = await params;
return (

{id}

);
};

export default Page;

It works

[subhanabdi]

hey any one help how can i resolve this error

src/app/blogs/[id]/page.tsx
Type error: Type 'Props' does not satisfy the constraint 'PageProps'.
Types of property 'params' are incompatible.
Type '{ id: string; }' is missing the following properties from type 'Promise': then, catch, finally, [Symbol.toStringTag]
Next.js build worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1

here is code

import { onGetCurrentDomainInfo } from '@/actions/settings';
import BotTrainingForm from '@/components/forms/settings/bot-training';
import SettingsForm from '@/components/forms/settings/form';
import InfoBar from '@/components/infobar';
import ProductTable from '@/components/products';
import { redirect } from 'next/navigation';

// Proper typing for dynamic route parameters
interface PageParams {
params: { domain: string };
searchParams?: { [key: string]: string | string[] | undefined };
}

export default async function DomainSettingsPage({ params }: PageParams) {
const domainInfo = await onGetCurrentDomainInfo(params.domain);

if (!domainInfo) {
redirect('/dashboard');
return null;
}

const domain = domainInfo.domains?.[0] || {};

return (
<>

<SettingsForm
plan={domainInfo.subscription?.plan || ''}
chatBot={domain.chatBot || null}
id={domain.id || ''}
name={domain.name || ''}
/>
{domain.id && }
{domain.id && <ProductTable id={domain.id} products={domain.products || []} />}

</>
);
}

[wassim01jr]

GENIUS AND A LIFE SAVER

[danielgrahamboaz]

The issue still persists on Vercel

[ss-sathya]

@danielgrahamboaz I was also facing the same issue. I’ve tried multiple ways, but it’s still not resolved. Did you find any other solution?

[danielgrahamboaz]

I haven't yet found a solution. On Apr 24, 2025 10:04 AM, Sathya ***@***.***> wrote: @danielgrahamboaz I was also facing the same issue. I’ve tried multiple ways, but it’s still not resolved. Did you find any other solution? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ss-sathya]

Let me know if you find a solution; if I find one, I'll let you know

[danielgrahamboaz]

SureOn Apr 24, 2025 10:54 AM, Sathya ***@***.***> wrote: Let me know if you find a solution; if I find one, I'll let you know —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ss-sathya]

export default async function Post({ params }: { params: { slug: string } }) {
const resolvedParams = await params;
const slug = resolvedParams.slug;
}

[danielgrahamboaz]

Here

import { Metadata } from "next";
import { CaseDetails } from "./components/case-details";

export const metadata: Metadata = {
  title: "Case Details",
  description: "View and manage case details",
};

type Params = { id: string };

export default async function Page({ params }: { params: Promise<Params> }) {
  const { id } = await params;
  return <CaseDetails id={id} />;
}

[izunwaonu]

import { Metadata } from "next";
import { CaseDetails } from "./components/case-details";

export const metadata: Metadata = {
title: "Case Details",
description: "View and manage case details",
};

type Params = { id: string };

export default async function Page({ params }: { params: Params }) {
const { id } = params;
return ;
}

[izunwaonu]

Fix in a nutshell

• Typed params as a plain object (Params) instead of Promise, because Next.js passes { params, searchParams } synchronously.
• Dropped the unnecessary await params and read the id directly with const { id } = params;.
• Aligning the runtime usage (no await) with the TypeScript annotation eliminates the “does not satisfy the constraint 'PageProps'” error, so the page now builds cleanly.

[ss-sathya]

I'm still facing the same error.

Error: Route "/blog/[slug]" used params.slug. params should be awaited before using its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis
at Page (c:\Users\softsuave-pc\Desktop\nextjs-contentful\src\app\blog[slug]\page.tsx:46:10)
44 |
45 | export default async function Page({ params }: { params: Params }) {

46 | const { slug } = params;

[danielgrahamboaz]

Yeah me too On Apr 24, 2025 11:39 AM, Sathya ***@***.***> wrote: I'm still facing the same error. Error: Route "/blog/[slug]" used params.slug. params should be awaited before using its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis at Page (c:\Users\softsuave-pc\Desktop\nextjs-contentful\src\app\blog[slug]\page.tsx:46:10) 44 | 45 | export default async function Page({ params }: { params: Params }) { 46 | const { slug } = params; —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ss-sathya]

I have tried it this way too, but no use

[danielgrahamboaz]

Did it work?On Apr 24, 2025 11:57 AM, Sathya ***@***.***> wrote: I have tried it this way too: image.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[ss-sathya]

No

[rakib86]

update your page component to work with ### Next.js 15, which expects [params] to be a Promise that needs to be awaited.

here is the demo

import { notFound } from "next/navigation";
import type { Metadata } from "next";

interface PageParams {
subdomain: string;
}

export type ParamsType = Promise;

export async function generateMetadata({
params
}: {
params: ParamsType
}): Promise {
const { subdomain } = await params;
return {
title: ${subdomain} - Your App Name,
};
}

export default async function SubdomainPage({
params
}: {
params: ParamsType
}) {
const { subdomain } = await params;
console.log("SubdomainPage: Rendering for subdomain:", subdomain);

try {
if (!subdomain) {
console.log("SubdomainPage: Tenant not found");
notFound();
}

return (
  <div className="flex min-h-screen flex-col items-center justify-center p-4">
    <div className="bg-white border border-gray-200 rounded-lg p-6 max-w-md">
      <h1 className="text-2xl font-bold mb-4">Welcome to {subdomain}</h1>
      <p className="text-gray-700">
        This is the subdomain page for {subdomain}. You can customize this
        page as needed.
      </p>
    </div>
  </div>
);

} catch (error) {
console.error("SubdomainPage: Error loading tenant:", error);
return (

Error

There was an error loading this tenant. Please try again later.

);
}
}